Refactor CI workflows for multi-arch image builds #155
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Author
|
cc @SchSeba |
Author
|
@SchSeba @adrianchiris Could you please review this PR when you get a chance? |
Signed-off-by: Ashok Pariya <[email protected]>
ashokpariya0
force-pushed
the
multi-arch-build
branch
from
aa2f741 to
e066bff
Compare
Author
|
I have rebased the PR. Please review it. @adrianchiris @SchSeba |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, our workflow builds and tags images separately for each architecture (latest-amd64, latest-arm64, latest-ppc64le etc, and then combines them into a single latest tag(https://github.com/k8snetworkplumbingwg/ib-sriov-cni/pkgs/container/ib-sriov-cni).
These changes create multi-arch image with single tag.